Reviewing files that changed from the base of the PR and between 59b21cc and ba11be3.

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

• components/afosto/afosto.app.mjs (1 hunks)
• components/booking_experts/actions/add-guest-to-reservation/add-guest-to-reservation.mjs (1 hunks)
• components/booking_experts/actions/create-agenda-period/create-agenda-period.mjs (1 hunks)
• components/booking_experts/actions/get-complex-prices/get-complex-prices.mjs (1 hunks)
• components/booking_experts/actions/list-bookings/list-bookings.mjs (1 hunks)
• components/booking_experts/actions/list-inventory-objects/list-inventory-objects.mjs (1 hunks)
• components/booking_experts/actions/search-contacts/search-contacts.mjs (1 hunks)
• components/booking_experts/booking_experts.app.mjs (1 hunks)
• components/booking_experts/package.json (2 hunks)
• components/booking_experts/sources/booking-updated/booking-updated.mjs (1 hunks)
• components/booking_experts/sources/common/base-polling.mjs (1 hunks)
• components/booking_experts/sources/inventory-object-updated/inventory-object-updated.mjs (1 hunks)
• components/booking_experts/sources/new-booking-created/new-booking-created.mjs (1 hunks)
• components/booking_experts/sources/new-inventory-object-created/new-inventory-object-created.mjs (1 hunks)

• GitHub Check: Verify TypeScript components
• GitHub Check: Publish TypeScript components
• GitHub Check: pnpm publish
• GitHub Check: Lint Code Base

components/afosto/afosto.app.mjs (1)

11-11: Trailing newline only — OK.
No functional changes.

components/booking_experts/package.json (2)

3-3: Version bump to 0.1.0 — OK.
Matches the new surface area added in this PR.

---

15-17: Verify @pipedream/platform v3.1.0 API availability
Confirm that the specific exports your code relies on—such as axios imports and ConfigurationError—are present in @pipedream/platform version 3.1.0 (e.g. by reviewing the v3.1.0 source or changelog).

components/booking_experts/booking_experts.app.mjs (1)

186-254: Unable to verify nested endpoints due to missing credentials. The script returned only an errors array (no data) because BOOKING_EXPERTS_API_KEY and/or ADMIN_ID weren’t set. Provide valid values or consult the Booking Experts API docs to confirm whether these /administrations/{id}/… routes are correct.

components/booking_experts/actions/search-contacts/search-contacts.mjs (1)

1-9: Provide the official parameter list for /contacts/search/first
Share the Booking Experts API docs snippet that lists all supported query parameters (with exact names and casing) for the /contacts/search/first endpoint so we can confirm whether email, phone, and name are valid.

components/booking_experts/actions/list-inventory-objects/list-inventory-objects.mjs (1)

43-55: Include $ for request context and avoid sending undefined query params

Pass $ to the app method for logging/observability, and build params without undefined values to prevent sending "undefined" strings.
[ suggest_essential_refactor ]

-    const { data } = await this.bookingExperts.listInventoryObjects({
-      administrationId: this.administrationId,
-      params: {
-        "filter[name]": this.name,
-        "filter[labels]": this.labels
-          ? this.labels.join(",")
-          : undefined,
-        "page[number]": this.page,
-        "page[size]": this.perPage,
-      },
-    });
+    const params = {
+      ...(this.name && { "filter[name]": this.name }),
+      ...(this.labels?.length && { "filter[labels]": this.labels.join(",") }),
+      ...(this.page && { "page[number]": this.page }),
+      ...(this.perPage && { "page[size]": this.perPage }),
+    };
+    const { data } = await this.bookingExperts.listInventoryObjects({
+      $,
+      administrationId: this.administrationId,
+      params,
+    });

components/booking_experts/actions/create-agenda-period/create-agenda-period.mjs (3)

50-59: Make rentableId optional and validate that at least one relation is provided

API commonly requires either an inventory object or a rentable. Mark rentableId optional and enforce a guard in run.
[ suggest_essential_refactor ]

-    rentableId: {
+    rentableId: {
       propDefinition: [
         bookingExperts,
         "rentableId",
         (c) => ({
           administrationId: c.administrationId,
           inventoryObjectId: c.inventoryObjectId,
         }),
       ],
+      optional: true,
+      description: "Rentable to associate. Provide either this or an Inventory Object.",
     },

---

61-95: Add input validation (date order, required relationships) and build relationships conditionally

Prevent invalid requests and clearer errors.
[ suggest_essential_refactor ]

   async run({ $ }) {
-    const { data } = await this.bookingExperts.createAgendaPeriod({
+    const start = Date.parse(this.startDate);
+    const end = Date.parse(this.endDate);
+    if (Number.isNaN(start) || Number.isNaN(end) || start > end) {
+      throw new Error("Invalid dates: ensure Start Date and End Date are valid and start <= end.");
+    }
+    if (!this.rentableId && !this.inventoryObjectId) {
+      throw new Error("Provide either `rentableId` or `inventoryObjectId`.");
+    }
+
+    const relationships = {};
+    if (this.inventoryObjectId) {
+      relationships.inventory_object = { data: { type: "inventory_object", id: this.inventoryObjectId } };
+    }
+    if (this.rentableId) {
+      relationships.rentable = { data: { type: "rentable", id: this.rentableId } };
+    }
+
+    const { data } = await this.bookingExperts.createAgendaPeriod({
       $,
       administrationId: this.administrationId,
       type: this.type,
       data: {
         data: {
           type: "agenda_period",
           attributes: {
             label: this.label,
             start_date: this.startDate,
             end_date: this.endDate,
           },
-          relationships: {
-            inventory_object: this.inventoryObjectId
-              ? {
-                data: {
-                  type: "inventory_object",
-                  id: this.inventoryObjectId,
-                },
-              }
-              : undefined,
-            rentable: {
-              data: {
-                type: "rentable",
-                id: this.rentableId,
-              },
-            },
-          },
+          relationships,
         },
       },
     });

---

6-6: Confirm JSON:API type value

Ensure the payload’s resource "type": "agenda_period" matches Booking Experts’ expected resource type for the selected endpoint (e.g., maintenance vs external blocked).
[ request_verification ]
Would you like me to cross-check the docs and adjust the type accordingly?

components/booking_experts/actions/list-bookings/list-bookings.mjs (2)

61-73: Bug: references to undefined createdAt / updatedAt props; filter keys may send undefined

Either add these props or remove the filters and omit undefined values. Also pass $ and mark optional filters as optional.
[ raise_critical_issue ]

   props: {
     bookingExperts,
     administrationId: {
       propDefinition: [
         bookingExperts,
         "administrationId",
       ],
     },
     ownerId: {
       propDefinition: [
         bookingExperts,
         "ownerId",
         (c) => ({
           administrationId: c.administrationId,
         }),
       ],
-      description: "Filter by owner",
+      description: "Filter by owner",
+      optional: true,
     },
     channelId: {
       propDefinition: [
         bookingExperts,
         "channelId",
         (c) => ({
           administrationId: c.administrationId,
         }),
       ],
-      description: "Filter by channel",
+      description: "Filter by channel",
+      optional: true,
     },
@@
     reservationId: {
@@
       optional: true,
     },
+    createdAt: {
+      type: "string",
+      label: "Created At",
+      description: "Filter by created_at (e.g. `2025-08-01..2025-08-31` or exact ISO timestamp), if supported by the API.",
+      optional: true,
+    },
+    updatedAt: {
+      type: "string",
+      label: "Updated At",
+      description: "Filter by updated_at (range or exact), if supported by the API.",
+      optional: true,
+    },

   async run({ $ }) {
-    const { data } = await this.bookingExperts.listBookings({
-      $,
-      administrationId: this.administrationId,
-      params: {
-        "filter[owner]": this.ownerId,
-        "filter[channel]": this.channelId,
-        "filter[reservations]": this.reservationId,
-        "filter[created_at]": this.createdAt,
-        "filter[updated_at]": this.updatedAt,
-        "page[number]": this.page,
-        "page[size]": this.perPage,
-      },
-    });
+    const params = {
+      ...(this.ownerId && { "filter[owner]": this.ownerId }),
+      ...(this.channelId && { "filter[channel]": this.channelId }),
+      ...(this.reservationId && { "filter[reservations]": this.reservationId }),
+      ...(this.createdAt && { "filter[created_at]": this.createdAt }),
+      ...(this.updatedAt && { "filter[updated_at]": this.updatedAt }),
+      ...(this.page && { "page[number]": this.page }),
+      ...(this.perPage && { "page[size]": this.perPage }),
+    };
+    const { data } = await this.bookingExperts.listBookings({
+      $,
+      administrationId: this.administrationId,
+      params,
+    });

---

66-70: Verify filter param names against the API

Double-check whether the API expects singular vs plural keys (e.g., filter[reservation] vs filter[reservations]) and accepted date filter formats.
[ request_verification ]
I can adjust the params once confirmed.

components/booking_experts/sources/common/base-polling.mjs (2)

36-67: Pagination stops after first page; uninitialized hasMore and potential event loss on equal timestamps

Initialize hasMore, bind the resource fn, default-sort by timestamp if absent, and use >= to avoid skipping events sharing the same timestamp (dedupe will handle duplicates).
[ raise_critical_issue ]

-      const items = [];
-      let total, hasMore, count = 0;
+      const items = [];
+      let total, hasMore = true, count = 0;
-      args = {
+      args = {
         ...args,
         params: {
           ...args?.params,
+          // default to newest-first by timestamp if not provided
+          sort: args?.params?.sort ?? `-${tsField}`,
           "page[number]": 1,
           "page[size]": 100,
         },
       };
       do {
-        const { data } = await resourceFn(args);
+        const boundResource = this.getResourceFn().bind(this.bookingExperts);
+        const { data } = await boundResource(args);
         total = data?.length;
         if (!total) {
           break;
         }
-        for (const item of data) {
+        hasMore = true;
+        for (const item of data) {
           const ts = Date.parse(item.attributes[tsField]);
-          if (ts > lastTs) {
+          if (ts >= lastTs) {
             items.push(item);
             if (limit && ++count >= limit) {
               hasMore = false;
               break;
             }
           } else {
             hasMore = false;
             break;
           }
         }
-        args.params["page[number]"]++;
-      } while (hasMore && total === args.params["page[size]"]);
+        if (hasMore && total === args.params["page[size]"]) {
+          args.params["page[number]"]++;
+        } else {
+          hasMore = false;
+        }
+      } while (hasMore);

---

72-77: Anchor lastTs correctly to avoid dropping items

Keeping lastTs at the newest ts is fine with >= filtering plus unique dedupe. Consider persisting the newest ts across the page, not only the first item.
[ suggest_optional_refactor ]

-      this._setLastTs(Date.parse(items[0].attributes[tsField]));
+      const newestTs = Math.max(...items.map((i) => Date.parse(i.attributes[tsField])));
+      this._setLastTs(newestTs);

components/booking_experts/sources/new-booking-created/new-booking-created.mjs (2)

22-24: Bind the app method to preserve this context

Returning an unbound method will lose its this and likely throw at runtime. Bind to the app instance.
[ raise_critical_issue ]

-    getResourceFn() {
-      return this.bookingExperts.listBookings;
-    },
+    getResourceFn() {
+      return this.bookingExperts.listBookings.bind(this.bookingExperts);
+    },

---

26-32: Pass sort by created_at explicitly (already done) and consider adding $ if your app wrapper uses it

If the app method benefits from $, update base-polling to pass it or wrap here.
[ request_verification ]
Do you want me to extend the base to pass $ through to the app calls?

components/booking_experts/sources/booking-updated/booking-updated.mjs (1)

25-35: Confirmed base-polling uses getTsField() for checkpointing and the API consistently applies sort: "-updated_at"; no changes required.

components/booking_experts/actions/add-guest-to-reservation/add-guest-to-reservation.mjs (2)

79-80: Confirm JSON:API type value
The Booking Experts docs list this resource’s type as “reservation_guests” for the create‐guest endpoint; please double-check that using “guest” here is correct.

---

1-25: Verified: reservationId propDefinition and addGuestToReservation method are present
The reservationId prop is defined with async options scoped by administrationId, and the addGuestToReservation client method exists in the app.